Repository navigation
ci: wait out npm's processing delay when publishing - #493
Merged
Merged
Conversation
npm hides a new version for several minutes while it processes it. The publish step gave up when a registry request failed during that wait, and a retry then failed with E409 because npm refuses to publish the hidden version again. The step now publishes every package before verifying them, retries registry errors for up to 20 minutes, and accepts the E409 for a version that verification then confirms comes from the release commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
npm keeps a newly published version hidden for a few minutes while it processes it. During the
11.0.0-nitro-v1.0release, the publish step crashed when a registry request failed during that wait, after publishing the core package and before the vec package. Re-running the job then failed withE409 Cannot publish over previously staged version, because the core version still wasn't visible and npm refuses to publish it again until then.The publish step now publishes every pending package before verifying any of them, so their processing delays overlap. Verification polls for up to 20 minutes and keeps going through registry and connection errors. A retry that gets the staged E409 for a package keeps going, and verification still has to confirm the version records the release commit. The publish job's timeout goes from 30 to 45 minutes to fit the longer wait.
🤖 Generated with Claude Code